feat(navigation): allow passing QueryBuilder or QueryBuilderParams in fetchNavigation or <ContentNavigation>
#1206
Conversation
✅ Deploy Preview for nuxt-content ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Co-authored-by: Sébastien Chopin <[email protected]>
|
I love it as well! :) Thanks a lot @harlan-zw 😄 |
|
Hey @harlan-zw :) After a brief discussion with @farnabaz ; I remembered we had plans on supporting the same type of query format as I will still merge this PR after applying some changes as we want to support both: <script setup>
const queryBuilder = queryContent().where({ ... })
</script>
<template>
<ContentNavigation :query="queryBuilder" />
<!-- OR (upcoming) -->
<ContentNavigation :where="{ ... }" />
</template> |
|
Just added a test to cover your changes @harlan-zw, thank you again for this! |
Tahul
changed the title
query prop to be QueryBuilder instancefetchNavigation or <ContentNavigation>
This would definitely be the ideal case, having all components with the same prop API for querying would be a great DX improvement. |
… `fetchNavigation` or `<ContentNavigation>` (#1206) Co-authored-by: Sébastien Chopin <[email protected]> Co-authored-by: Yaël Guilloux <[email protected]>
🔗 Linked issue
❓ Type of change
📚 Description
The
ContentNavigationcomponent is typed to only allow you to provide the query asQueryBuilderParams. The DX of this isn't great as everywhere else in the doc aQueryBuilderis used withqueryContent.This is especially annoying when you want to show the
ContentNavigationwith a simple path prefix, as the user has to then figure out regex.The
fetchContentNavigationalready supports aQueryBuilder, so it's seems like this was the initial expectation of this prop anyway.I've added an example to highlight the use case
📝 Checklist